-
Notifications
You must be signed in to change notification settings - Fork 32
Add a check_write_permissions option to update function job/out 🐛 #8325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a check_write_permissions option to update function job/out 🐛 #8325
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #8325 +/- ##
==========================================
+ Coverage 85.12% 87.69% +2.57%
==========================================
Files 1825 1520 -305
Lines 70906 62779 -8127
Branches 1311 658 -653
==========================================
- Hits 60362 55057 -5305
+ Misses 10149 7489 -2660
+ Partials 395 233 -162
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
🧪 CI InsightsHere's what we observed from your CI run for c68204c. 🟢 All jobs passed!But CI Insights is watching 👀 |
services/web/server/src/simcore_service_webserver/functions/_functions_repository.py
Show resolved
Hide resolved
services/web/server/src/simcore_service_webserver/functions/_functions_repository.py
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thx!
|
@mergify queue |
🛑 Configuration not compatible with a branch protection settingThe branch protection setting |
|



What do these changes do?
While using the caching ability of function job status/output, there was an issue when a user only has read permission for function jobs. The repository layer was refusing to update the status/output coming from the comp backend in the db, used as cache, since the user didn't have write permission. I added an option to the update call to ignore the write permissions (the user can't control what is being written, the values are always coming from the comp backend)
Related issue/s
How to test
Give a user read-only access to a function job. Let user get status/output of the function job. This should succeed now.
Dev-ops
No changes